Skip to content

[avahi] Add plugin for the Avahi mDNS/DNS-SD stack - #4427

Open
suraj-cmd wants to merge 1 commit into
sosreport:mainfrom
suraj-cmd:add-avahi-plugin
Open

[avahi] Add plugin for the Avahi mDNS/DNS-SD stack#4427
suraj-cmd wants to merge 1 commit into
sosreport:mainfrom
suraj-cmd:add-avahi-plugin

Conversation

@suraj-cmd

Copy link
Copy Markdown
Contributor

Avahi is installed by default on Fedora, RHEL, Debian and Ubuntu, but sos has
no plugin for it and no other plugin references it. Neither its configuration
nor the services it advertises reach an sosreport, which matters when .local
name resolution or multicast service discovery is misbehaving.

Paths are taken from upstream. avahi-daemon/Makefile.am defines the
configuration file as $(pkgsysconfdir)/avahi-daemon.conf and the service
directory as $(pkgsysconfdir)/services, and static-hosts.c reads
AVAHI_CONFIG_DIR "/hosts".

Unit names come from the shipped units: avahi-daemon.service, which requires
avahi-daemon.socket, and avahi-dnsconfd.service.

avahi-browse --all --terminate --resolve records what the host can see on the
link at collection time, and avahi-daemon --check reports whether a daemon is
already running.

The daemon holds no credentials, so no forbidden paths or postproc handling are
needed.

Paths and unit names are taken from upstream rather than a running system.
avahi-browse --all --terminate --resolve produces network traffic at
collection time — if maintainers would prefer that behind --all-logs or a
plugin option rather than run by default, I am happy to move it.


Please place an 'X' inside each '[]' to confirm you adhere to our Contributor Guidelines

  • Is the commit message split over multiple lines and hard-wrapped at 72 characters?
  • Is the subject and message clear and concise?
  • Does the subject start with [plugin_name] if submitting a plugin patch or a [section_name] if part of the core sosreport code?
  • Does the commit contain a Signed-off-by: First Lastname email@example.com?
  • Are any related Issues or existing PRs

Avahi is installed by default on Fedora, RHEL, Debian and
Ubuntu, but sos has no plugin for it and no other plugin
references it. Neither its configuration nor the services it
advertises reach an sosreport, which matters when .local name
resolution or multicast service discovery is misbehaving.

Paths are taken from upstream. avahi-daemon/Makefile.am defines
the configuration file as $(pkgsysconfdir)/avahi-daemon.conf
and the service directory as $(pkgsysconfdir)/services, and
static-hosts.c reads AVAHI_CONFIG_DIR "/hosts".

Unit names come from the shipped units: avahi-daemon.service,
which requires avahi-daemon.socket, and avahi-dnsconfd.service.

"avahi-browse --all --terminate --resolve" records what the
host can see on the link at collection time, and
"avahi-daemon --check" reports whether a daemon is already
running.

The daemon holds no credentials, so no forbidden paths or
postproc handling are needed.

Signed-off-by: Suraj Patil <surajpatil522@gmail.com>
@packit-as-a-service

Copy link
Copy Markdown

Congratulations! One of the builds has completed. 🍾

You can install the built RPMs by following these steps:

  • sudo dnf install -y 'dnf*-command(copr)'
  • dnf copr enable packit/sosreport-sos-4427
  • And now you can install the packages.

Please note that the RPMs should be used only in a testing environment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant